Skip to content

blobs: use the 00cb blob set for 06cb:00b7 - #9

Merged
SimpleX-T merged 2 commits into
SimpleX-T:feat/sensor-type-0xd51from
Primal-Origin:fix-00b7-reset-blob
Nov 19, 2026
Merged

SimpleX-T merged 2 commits into
SimpleX-T:feat/sensor-type-0xd51from
Primal-Origin:fix-00b7-reset-blob

Conversation

@Primal-Origin

@Primal-Origin Primal-Origin commented Nov 14, 2026 •

Copy link
Copy Markdown

Device: HP EliteBook x360 1040 G6, USB 06cb:00b7 (sensor type 0x969), CachyOS, Python 3.14.

Problem: after clearing the sensor with the BIOS fingerprint reset, init_flash fails at the reset_blob step with status 0404. factory_reset in sensor.py hits the same rejection. Related upstream thread: uunicorn#225.

Change: in blobs.py, 06cb:00b7 now loads blobs_00cb instead of blobs_9a. blobs_00cb matches blobs_9a except for reset_blob (checked for the other three blobs), and its reset_blob is accepted by this chip while 9a's is rejected with 0404. Doing it in blobs.py covers init_flash.py and factory_reset. An earlier version of this PR special-cased init_flash.py; that is reverted.

Testing: with this change the service stays up, fprintd-enroll completes and fprintd-verify works. Another 06cb:00b7 owner (Karloss1234) reports the same blob as the only one their chip accepts.

Fixes the 0404 failure at reset_blob on HP EliteBook x360 1040 G6. Tested only on that laptop.
@Karloss1234

Karloss1234 commented Nov 17, 2026 •

Copy link
Copy Markdown

blobs_00cb.py is the only blob which my 06cb:00b7 0x969 chip accepts with status 0000 after
assert_status(usb.cmd(reset_blob)),
although when the chip actions the blob with assert_status(usb.cmd(b'\x10' + b'\0' * 0x61)) is returns 0404, which means correct blob, but no factory reset for what ever reason.
It is also the blob bundled inside the installation driver, 6_07f_hp_cmit_mis_qm.xpfwext.

Also, blobs.py is where your code change should go. This is where the table for all the different hardware vs correct blob is specified.

@Primal-Origin

Copy link
Copy Markdown
Author

@Karloss1234 Thanks for testing. That matches what I saw on my 00b7. I'll move the change into blobs.py where the hardware-to-blob table lives and push an update to this branch.

Same blobs as blobs_9a except reset_blob, which this chip accepts (9a's is rejected with 0404). Done in blobs.py so factory_reset in sensor.py gets it too, and the init_flash.py special case is reverted. Suggested by Karloss1234 in the PR.
@Primal-Origin Primal-Origin changed the title init_flash: use the 00cb reset blob for 06cb:00b7 blobs: use the 00cb blob set for 06cb:00b7 Nov 18, 2026
@Primal-Origin

Copy link
Copy Markdown
Author

Pushed an update moving the change into blobs.py as you suggested @Karloss1234 , thanks.

@SimpleX-T
SimpleX-T merged commit 0bab307 into SimpleX-T:feat/sensor-type-0xd51 Nov 19, 2026
@SimpleX-T

Copy link
Copy Markdown
Owner

Merged — thanks @Primal-Origin and @Karloss1234. While reviewing I checked the blob sets: blobs_00cb and blobs_d51 have a byte-identical reset_blob (11973 B, sha256 7f379b16…), and all four blobs other than reset_blob are identical to blobs_9a. So this is the correct HP payload for both 00b7 variants — it is the same blob gfiguero independently extracted from HP's DLL and saw accepted on a factory-empty 0xd51 / FM-3439-001. The previous blobs_9a mapping was sending Lenovo's 12037 B blob, which explains the 0404. Zero-partition 0x969 provisioning is still gated by the identity check in init_flash(), so this does not open a new destructive path. I'll follow up with a comment fix and a regression test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants